Skip to content

Remove Plausible analytics integration #7525

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 4, 2025

Conversation

jnsdls
Copy link
Member

@jnsdls jnsdls commented Jul 4, 2025

Remove Plausible Analytics Integration

This PR removes the Plausible Analytics integration from our applications:

  • Removed next-plausible dependency from the dashboard app
  • Removed Plausible script tags from dashboard, playground-web, and portal layouts
  • Removed the Plausible proxy configuration from the Next.js config
  • Updated the webpack configuration to work without the Plausible proxy wrapper

PR-Codex overview

This PR focuses on removing the next-plausible package from various files in the codebase, including configuration and layout files, and updates dependency references in package.json and pnpm-lock.yaml.

Detailed summary

  • Removed next-plausible dependency from apps/dashboard/package.json, pnpm-lock.yaml.
  • Eliminated PlausibleProvider component from apps/dashboard/src/app/(app)/layout.tsx and apps/portal/src/app/layout.tsx.
  • Removed Script imports and their usage in multiple layout files.
  • Updated next.config.ts to exclude withPlausibleProxy configuration.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Summary by CodeRabbit

  • Chores
    • Removed Plausible analytics integration and related dependencies from the dashboard.
    • Removed external script loading from the layouts of the playground-web and portal apps.

@jnsdls jnsdls mentioned this pull request Jul 4, 2025
Copy link

vercel bot commented Jul 4, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
docs-v2 ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 4, 2025 2:44am
thirdweb_playground ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 4, 2025 2:44am
thirdweb-www ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 4, 2025 2:44am
2 Skipped Deployments
Name Status Preview Comments Updated (UTC)
nebula ⬜️ Skipped (Inspect) Jul 4, 2025 2:44am
wallet-ui ⬜️ Skipped (Inspect) Jul 4, 2025 2:44am

Copy link

changeset-bot bot commented Jul 4, 2025

⚠️ No Changeset found

Latest commit: 9fba016

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Contributor

coderabbitai bot commented Jul 4, 2025

Walkthrough

This change removes all tracking, analytics, and external script integrations related to Plausible and a third-party script from the dashboard, playground-web, and portal applications. It eliminates related dependencies, plugins, providers, and script tags from configuration files and layout components, without altering any public APIs or exported entities.

Changes

File(s) Change Summary
apps/dashboard/next.config.ts Removed Plausible proxy integration from Next.js config; now only uses Sentry and BundleAnalyzer.
apps/dashboard/package.json Removed "next-plausible" dependency.
apps/dashboard/src/app/(app)/layout.tsx Removed PlausibleProvider import and usage from RootLayout.
apps/playground-web/src/app/layout.tsx, apps/portal/src/app/layout.tsx Removed external thirdweb script import and usage from RootLayout components.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant DashboardApp
    participant PlausibleProxy
    participant ThirdwebScript

    Note over User,DashboardApp: Previous Flow (Dashboard)
    User->>DashboardApp: Load page
    DashboardApp->>PlausibleProxy: Initialize Plausible tracking
    DashboardApp->>User: Render page with PlausibleProvider

    Note over User,DashboardApp: New Flow (Dashboard)
    User->>DashboardApp: Load page
    DashboardApp->>User: Render page (no Plausible tracking)

    Note over User,Playground/Portal: Previous Flow (Playground/Portal)
    User->>Playground/Portal App: Load page
    Playground/Portal App->>ThirdwebScript: Load external script
    Playground/Portal App->>User: Render page with script tag

    Note over User,Playground/Portal: New Flow (Playground/Portal)
    User->>Playground/Portal App: Load page
    Playground/Portal App->>User: Render page (no external script)
Loading

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fa3c37a and 9fba016.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (5)
  • apps/dashboard/next.config.ts (1 hunks)
  • apps/dashboard/package.json (0 hunks)
  • apps/dashboard/src/app/(app)/layout.tsx (0 hunks)
  • apps/playground-web/src/app/layout.tsx (0 hunks)
  • apps/portal/src/app/layout.tsx (0 hunks)
💤 Files with no reviewable changes (4)
  • apps/dashboard/src/app/(app)/layout.tsx
  • apps/dashboard/package.json
  • apps/portal/src/app/layout.tsx
  • apps/playground-web/src/app/layout.tsx
🚧 Files skipped from review as they are similar to previous changes (1)
  • apps/dashboard/next.config.ts
⏰ Context from checks skipped due to timeout of 90000ms (7)
  • GitHub Check: E2E Tests (pnpm, webpack)
  • GitHub Check: E2E Tests (pnpm, esbuild)
  • GitHub Check: E2E Tests (pnpm, vite)
  • GitHub Check: Size
  • GitHub Check: Unit Tests
  • GitHub Check: Lint Packages
  • GitHub Check: Analyze (javascript)
✨ Finishing Touches
  • 📝 Generate Docstrings

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions github-actions bot added Dashboard Involves changes to the Dashboard. Playground Changes involving the Playground codebase. Portal Involves changes to the Portal (docs) codebase. labels Jul 4, 2025
@jnsdls jnsdls marked this pull request as ready for review July 4, 2025 01:50
@jnsdls jnsdls requested review from a team as code owners July 4, 2025 01:50
Copy link
Member Author

jnsdls commented Jul 4, 2025


How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

  • merge-queue - adds this PR to the back of the merge queue
  • hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

Copy link
Contributor

github-actions bot commented Jul 4, 2025

size-limit report 📦

Path Size Loading time (3g) Running time (snapdragon) Total time
thirdweb (esm) 63.2 KB (0%) 1.3 s (0%) 235 ms (+85.56% 🔺) 1.5 s
thirdweb (cjs) 352.68 KB (0%) 7.1 s (0%) 948 ms (+8.84% 🔺) 8.1 s
thirdweb (minimal + tree-shaking) 5.69 KB (0%) 114 ms (0%) 110 ms (+1540.87% 🔺) 224 ms
thirdweb/chains (tree-shaking) 526 B (0%) 11 ms (0%) 18 ms (+730.67% 🔺) 28 ms
thirdweb/react (minimal + tree-shaking) 19.57 KB (0%) 392 ms (0%) 74 ms (+411.47% 🔺) 465 ms

Copy link

codecov bot commented Jul 4, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 51.97%. Comparing base (4b8badb) to head (9fba016).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #7525   +/-   ##
=======================================
  Coverage   51.97%   51.97%           
=======================================
  Files         952      952           
  Lines       64212    64212           
  Branches     4239     4238    -1     
=======================================
  Hits        33375    33375           
  Misses      30730    30730           
  Partials      107      107           
Flag Coverage Δ
packages 51.97% <ø> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Base automatically changed from 07-03-upgrade_dependencies to main July 4, 2025 02:22
@jnsdls jnsdls force-pushed the Remove_Plausible_analytics_integration branch from d3ab94c to fa3c37a Compare July 4, 2025 02:22
@vercel vercel bot temporarily deployed to Preview – wallet-ui July 4, 2025 02:23 Inactive
Copy link
Contributor

graphite-app bot commented Jul 4, 2025

Merge activity

# Remove Plausible Analytics Integration

This PR removes the Plausible Analytics integration from our applications:

- Removed `next-plausible` dependency from the dashboard app
- Removed Plausible script tags from dashboard, playground-web, and portal layouts
- Removed the Plausible proxy configuration from the Next.js config
- Updated the webpack configuration to work without the Plausible proxy wrapper

<!-- start pr-codex -->

---

## PR-Codex overview
This PR removes the usage of `next-plausible` from various files and updates dependencies accordingly. It also cleans up the code by removing unnecessary `<head>` elements and script imports across multiple layout files.

### Detailed summary
- Removed `next-plausible` dependency from `apps/dashboard/package.json`.
- Deleted `<Script>` components related to Plausible from `layout.tsx` files in `apps/playground-web`, `apps/dashboard`, and `apps/portal`.
- Cleaned up `next.config.ts` by removing `withPlausibleProxy`.
- Updated `pnpm-lock.yaml` to reflect the removal of `next-plausible`.

> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`

<!-- end pr-codex -->

<!-- This is an auto-generated comment: release notes by coderabbit.ai -->

## Summary by CodeRabbit

* **Chores**
  * Removed Plausible analytics integration and related dependencies from the dashboard.
  * Removed external script loading from the layouts of the playground-web and portal apps.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Dashboard Involves changes to the Dashboard. Playground Changes involving the Playground codebase. Portal Involves changes to the Portal (docs) codebase.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants